Current Behavior

• If the workspace-generator used any utils that lived in the tools folder, their import paths would be broken
• If the workspace has an npmScope, the import path for the plugin is ${npmScope}/workspace-plugin
• The workspace-generator wrapper was clobbering any arguments called "name" since there was a positional called name as well.
  • This was something that was worked around in the previous yargs config that I did not notice

Expected Behavior

• If the workspace-generator used any utils that lived in the tools folder, their import paths are not broken
• If the workspace has an npmScope, the import path for the plugin is @${npmScope}/workspace-plugin
• You can pass --name to converted generators

Related Issue(s)

Fixes #